---
title: Downloads
x-toc-enable: true
...

Information about specific changes in each Retroboot release, can be found
at [docs/release.md](docs/release.md)

Git (recommended for developers and power users)
------------------------------------------------

The Git repository is recommended if you want the most up to date version,
but you will have to build it from source. Git is preferred for development.

<https://notabug.org/retroboot/retroboot/>

If you wish to compile Retroboot from source code, refer to
this guide for [how to compile retroboot source code](docs/git/).
Information about the build system is available on the
[Retroboot Maintainance Manual](docs/maintain/).

Download pre-compiled releases (recommended for most people) {#https}
------------------------------------------------------------

The latest release available is `20210106beta`, which is a beta release.

### Download Retroboot releases from one of these mirrors:

[https://retroboot.org/release/](release/) (Retroboot.org official mirror, UK)

[https://mirrors.freedragon.club/retroboot/](https://mirrors.freedragon.club/retroboot/) (server location: Hong Kong)

Be sure to verify the GPG signature! (see below)

Retroboot is looking for people to provide download mirrors. See Rsync info on
this page.

GPG signing key
---------------

Releases are signed with GPG. This means that you can verify whether you have
the correct archive and that it has not been tampered with. The following key
is available for the purpose, listed on public key servers.

Download the key in GNU+Linux:

    gpg --recv-keys 0xD0C62464FA8B4856

Full key fingerprint: `98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856`

When you've followed the above instruction, you have the key. This can be used
to verify the authenticity of archives that you have downloaded (or at the very
least, ensure that they were provided officially by the Retroboot project).
All releases are *signed* with this key, including beta releases.

When you download Retroboot, an accompanying `.sig` file will be available with
every file. For instance, `retroboot20210106beta_src.tar.xz` will also have
a file named `retroboot20210106beta_src.tar.xz.sig` available.

Verify the GPG signature on a source code archive:

    gpg --verify retrobootVERSION_src.tar.xz.sig

Verify the GPG signature on a ROM archive:

    gpg --verify retrobootVERSION_roms.tar.xz.sig

Do you have a mirror?
---------------------

Let us know! We will add it here.

If you wish to create a new mirror of the Retroboot releases, you can use
*rsync*. See: [rsync mirror list](#rsync).

RSYNC mirrors {#rsync}
-------------

Useful for mirroring Retroboot's entire set of release archives. You can put
an rsync command into crontab and pull the files into a directory on your
web server.

*It is highly recommended that you use the retroboot.org mirror*, if you wish
to host an official mirror. Otherwise, if you simply want to create your own
local mirror, you should use one of the other mirrors, which sync from
retroboot.org.

<rsync://rsync.retroboot.org/retroboot/> (Retroboot.org official mirror, UK)

<rsync://mirrors.freedragon.club/retroboot/> (server location: Hong Kong)

Are you running a mirror? Contact the retroboot project, and the link will be
added to this page!

If you want to create a mirror, first create a directory in the webroot of the
directory for your website.

To automatically update your mirror, add this in your crontab:

    rsync -avz --delete-after rsync://rsync.retroboot.org/retroboot/ /path/to/your/directory/

NOTE: The final `/` on `/path/to/your/directory/` is *very important*. The
`--delete-after` parameter is also very important.

Now, verify that the files appear on your URL e.g. `https://foo.com/retroboot/`

**NOTE: We only link to https and rsync mirrors. Unencrypted HTTP mirrors will
not be linked here (encrypted rsync mirrors are not possible, but releases have
GPG keys included with them, which mitigates this)**
